home *** CD-ROM | disk | FTP | other *** search
- Date: Sun, 12 Jun 94 15:55 CDT
- From: ekl@sdf.lonestar.org (Evan K. Langlois)
- To: gem-list@world.std.com
- Subject: Re: what about this?
- Precedence: bulk
-
- No, implementing a double "keyboard" click does not mean a delay exactly.
- It means you have another evnt_multi with a small timer event which is
- not the same as a delay. A delay is fixed and cannot be short-cutted.
- If you type something else or click or move the mouse before the GEM timer
- expires then you have a single key-click plus the next event, if the next
- event is another keyboard click, and is the same exact key as before, THEN
- you have a double-key-click. If the timer expires, then you have a single
- key click.
-
- By using this method, someone typing real fast will still not get the delay
- as the next event cancels the delay, and the faster you type the double
- key, the faster the program reacts. Also, it may be a good idea to revert
- the idea. So that a double-click is WITHOUT the dialog, and the single-
- click is WITH the dialog. The reasoning for this is simple, users will
- "wait" for a dialog but want things to be fast if its automatic, due to
- the way the timeout will expire at the next event.
-
- Get it? Seems like a good idea.
-
- ~.
-